[Az.BillingBenefits] Update generation tool version: autorest.powershell V3 -> V4 #27466
Conversation
| Thanks for your contribution! The pull request validation has started. Please revisit this comment for updated status. |
| variant: ^(Create|Update)(?!.*?(Expanded|JsonFilePath|JsonString)) | ||
| remove: true | ||
| - where: | ||
| variant: ^CreateViaIdentity$|^CreateViaIdentityExpanded$|^ValidateViaIdentitySavingsPlanOrder$|^ValidateViaIdentitySavingsPlanOrderExpanded$ |
There was a problem hiding this comment.
Please merge validate* variants with the first directive by adding something like Create|Update|Validate
| remove: true | ||
| - where: | ||
| variant: ^CreateViaIdentity$|^CreateViaIdentityExpanded$|^ValidateViaIdentitySavingsPlanOrder$|^ValidateViaIdentitySavingsPlanOrderExpanded$ | ||
| variant: ^CreateViaIdentity$|^CreateViaIdentityExpanded$|^ValidateViaIdentitySavingsPlanOrderExpanded$|^ElevateViaIdentity$ |
There was a problem hiding this comment.
Why to remove ^ValidateViaIdentitySavingsPlanOrderExpanded$|^ElevateViaIdentity$
There was a problem hiding this comment.
Removed the cmdlets “Invoke-AzBillingBenefitsElevateSavingPlanOrder”, “Invoke-AzBillingBenefitsSavingsPlanPurchaseValidation” and “Invoke-AzBillingBenefitsSavingsPlanUpdateValidation” which are mainly part of the syntax in “XXXViaIdentity”.
This is because these three cmdlets now generate syntax that supports “ValidateViaJsonFilePath”, “ValidateViaJsonString”.
There was a problem hiding this comment.
Removed the cmdlets “Invoke-AzBillingBenefitsElevateSavingPlanOrder”, “Invoke-AzBillingBenefitsSavingsPlanPurchaseValidation” and “Invoke-AzBillingBenefitsSavingsPlanUpdateValidation” which are mainly part of the syntax in “XXXViaIdentity”.
This is because these three cmdlets now generate syntax that supports “ValidateViaJsonFilePath”, “ValidateViaJsonString”.
…l v3->v4
Description
Mandatory Checklist
Please choose the target release of Azure PowerShell. (⚠️ Target release is a different concept from API readiness. Please click below links for details.)
Check this box to confirm: I have read the Submitting Changes section of
CONTRIBUTING.mdand reviewed the following information:ChangeLog.mdfile(s) appropriatelysrc/{{SERVICE}}/{{SERVICE}}/ChangeLog.md.## Upcoming Releaseheader in the past tense.ChangeLog.mdif no new release is required, such as fixing test case only.